Thank you for the PR! I only think about it to split the path and the "stats" in separate lines, because the path could be very long. Can you please split it in separate lines?

Landscape mobile, dropping the filament usage to keep the UI clean:

I would suggest keepping then filament usage also on mobile. Very helpful to check if enough filament is left if I want to start a job one more time.

Default state, show the total for the entire directory

I would suggest to hide the state if no job is selected. The UI would be more clean and it can be easily shown if all are selected.
Perhaps only show 1 decimal on filament and no seconds on print time to save space.

I only think about it to split the path and the "stats" in separate lines, because the path could be very long.

Seperate lines would take a lot of space on mobile, I would rather suggest to shorten the description
Print Time: 5h 5min Filament: 135.6g Free Disk: 8.4 GB

but if you only display it, when files are selected, i see no problem with a separate line. then you have also enough space to display:

3 files selected, Print Time: 5h 5min,  Filament: 135.6g

and path & free disk space will be in the first line without any change.

but if you only display it, when files are selected, i see no problem with a separate line. then you have also enough space to display:

3 files selected, Print Time: 5h 5min,  Filament: 135.6g

and path & free disk space will be in the first line without any change.

Seems fine for me 👍

To make it a second line, there are some downsides as well:

• If the 2nd line is not initially visible, then selecting an item would move the entire UI below it down by a line height, which I could see being annoying to users, making selecting other items a bit of a "moving target".
• If the 2nd line is initially there but empty and only populated once a selection is made, it just adds a bunch of extra whitespace that I suspect would look odd (I saw this because my first implementation was actually to add an additional spreadsheet-style "Sum" row to the table, but there was way too much whitespace and it looked odd).

I had considered putting the data in the bottom left, on the same row as the pagination controls, but that would likely create some of the same issue.

A third idea I had 🤔, but haven't experimented with, was to move everything "stats" related to a new panel below the file selection panel. This panel would work similar to the way the "History" page does, where there are some graphs, and changing the selection changes the content of the graph. This would be more work, but would get out of the problem of putting too much extra information in the files table, and also allow users to collapse the panel if they didn't want that data..

I'm attaching a (really bad) quick sketch of what I'm takling about. This new panel could have a pie chart of printed vs. not printed, and a table of filament length, filament weight, and print time of the selected files. I'm sure other things could be added in the future as well.

Is adding the panel with the charts necessary?

My main problem with this is that if you don't select any files, mainsail doesn't have all the metadata, but only the metadata from the currently visible files (or metadata pulled since the last refresh). The statistics wouldn't make sense without having a file selected.

As an alternative, it would occur to me that you make the two lines above by default and then split them:

• 1. line: path
• 2. line (per default): 0 selected files ... free disk space
• 2nd line (with files selected): 3 selected files ... print time ... filament ... free disk space

As an alternative, it would occur to me that you make the two lines above by default and then split them:

* 1. line: path

* 2. line (per default): 0 selected files ... free disk space

* 2nd line (with files selected): 3 selected files ... print time ... filament ... free disk space

I like this idea.

@EmJay276 @tstone any progess here?

@meteyou
I think@tstone is developing this PR.
But I can have a look at necessary changes.

@EmJay276 this would be nice. otherwise I have to implement this feature, but feel free to create a new PR with this feature.

Any news here?

i will close this PR, because of no response...